Posts tagged “ai agents”

A step-by-step method for having your coding agent walk your product like a new user and hand you the findings as a review link, PDF, or markdown.

Three defensible rules for framing a cropped still so an agent identifies the right component, plus what goes wrong when you ignore each one.

Vague selectors, no screenshot, five bugs in one message: the patterns that make Bolt guess wrong, and the concrete fix for each.

An agent will happily edit the wrong element if your markdown bug report is vague. Here are the specific mistakes that cause it and the concrete fix for each.

An agent can only act on what your screenshot points at. Here is how to crop, pin, and word a comment so the change lands on the intended element.

Vague feedback wastes an agent's time. Here is how to capture a screen, name the problem, and hand over text the agent can turn into a fix.

Vibecoding stalls when the loop between seeing a problem and telling the agent about it is sloppy. Here is what breaks and how to fix it.

Claude Code will happily act on bad input. Here are five specific ways UI feedback goes wrong before it reaches the agent, and what to send instead.

Coding agents cannot watch your Loom. They need text with structure. Here is why video breaks the handoff and what actually lands as actionable input.